<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
  <meta http-equiv="Content-Language" content="en-us">
  <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
  <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
  <meta name="ProgId" content="FrontPage.Editor.Document"><title>Test Pass One</title></head>
<body>
<h1>Test Pass One: JDT UI, JDT Text, Platform Compare, Platform Text,
and Platform Search</h1>
<h3>Testers: Martin, Dani, Markus, Christof, David, Benjamin, Tobias,
Tom, Dirk<br>
</h3>
<h2>Goal</h2>
<ul>
  <li>test new 3.1 M7 functionality<br>
  </li>
  <li>test Java 5.0 functionality. Whenever you create some test code
please use 5.0 language features whenever possible. For example add a
type parameter to every new class, ...</li>
  <li><font color="#000000">test corner cases</font></li>
  <li>test setups which we typically don't use during development (for
example no Plug-in development)</li>
  <li><font color="#000000">handling of error situations</font>
    <ul>
      <li><font color="#000000">watch log</font></li>
      <li><font color="#000000">error messages</font></li>
    </ul>
  </li>
</ul>
<h2>Setup / Introduction</h2>
<h3><span style="font-weight: bold;">Build</span></h3>
&nbsp;&nbsp;&nbsp; Eclipse-SDK-I20050509-2010
<h3>Platforms</h3>
<ul>
  <li>Linux-GTK FedoraCore (Tom)<br>
</li>
  <li>Mac OS X (Christof)<br>
  </li>

  <li>Windows XP (all others test)<br>
  </li>
</ul>
<h3>General Items (everybody)</h3>
<ul>
  <li>Whenever you have to fill in data in dialogs try to fool the
dialog by providing incomplete or bogus input</li>
  <li>Watch for view updating (package explorer, browsing perspective,
outliner) when source content gets changed</li>
</ul>
<h3>Use of different fonts (everybody)</h3>
<ul>
  <li>change font for text editor and dialogs to different font</li>
  <li>check that dialogs are rendered correctly
    <ul>
      <li>specified dialog font is used</li>
      <li>no buttons and labels clipped</li>
    </ul>
  </li>
</ul>
<h3>Test Multiple Monitor setup (Martin)</h3>
<ul>
  <li>detached views</li>
  <li>dialogs pop up on correct monitor</li>
</ul>
<h3>Workspace Setup</h3>
<p>Setup workspace in a way unusual compared to your normal setup.
Testing should take place in one of the following workspace setups.
When setting up the workspace test also the functionality to setup
this workspace style:</p>
<ul>
  <li>use external projects (Benjamin, Tobias)</li>
  <li>use linked resources (David)
    <ul>
      <li><font color="#000000">linked output folders</font></li>
      <li><font color="#000000">linked source folders</font></li>
      <li><font color="#000000">linked and nested source folders</font></li>
      <li>test rendering in views<font color="#000000"></font></li>
      <li><font color="#000000">linked class folders</font></li>
    </ul>
  </li>
  <li>use multiple output folder (Christof)</li>
  <li>use combination of exclusion &amp; inclusion filters (Martin)</li>
  <li>use user defined library containers (JUnit as a user defined
library) (Dirk)
    <ul>
      <li>quick fixes for unbound user libraries</li>
      <li>quick fixes for build path problems</li>
    </ul>
  </li>
  <li>full source workspace (Markus)</li>
</ul>
<h3>Java Editor in Single Method mode (Martin, Benjamin, Tobias, Markus)</h3>
<ul>
  <li>half of the team should test with editor in single edit mode</li>
  <li>corner case
    <ul>
      <li>segmented mode, formatting, undo/redo</li>
    </ul>
  </li>
</ul>
<h3>Multiple Windows (Tobias, Markus, David, Dirk)</h3>
<ul>
  <li>half of the team tests with multiple windows.</li>
  <li>switch between windows for different actions</li>
  <li>watch for wrong window popping to front</li>
  <li>watch for wrong dialog parenting</li>
</ul>
<h3>Multiple Editor Areas (Tom, Markus, Benjamin)</h3>
<ul>
  <li> test with multiple editor areas, i.e. multiple editor tab folders</li>
  <li> watch for focus problems</li>
  <li> watch for positioning problems when opening dialogs and info pops</li>
</ul>
<h3>Java Perspective / Browsing Perspective / Working Set mode</h3>
<ul>
  <li>third of the team tests in browsing perspective (Dirk, Tom, David)<br>
  </li>
  <li>third of the team tests in Java perspective using project mode in
package explorer (Martin, Tobias, Benjamin)<br>
  </li>
  
  <li>third of the team tests in Java perspective using the working set
mode in the package explorer (Dani, Christof, Markus)<br>
  </li>

</ul>
<h3>Automatic workspace refresh (Benjamin, Markus, Christof, Dirk)</h3>
<ul>
  <li>half of the team tests with automatic workspace refresh enabled
(<span style="font-weight: bold;">Preferences &gt; Workbench &gt; Refresh</span> workspace automatically</li>
</ul>
<h2>3.1 M7 items</h2>
<h4>Bug verification (all)<br>
</h4>
<ul>
  <li>Verify all P1 &amp; P2 bugs fixed during M7 (total 27) (<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=JDT&amp;component=Text&amp;component=UI&amp;target_milestone=3.1+M7&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;priority=P1&amp;priority=P2&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">JDT/UI
&amp; JDT/Text</a>, <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=Platform&amp;component=Text&amp;target_milestone=3.1+M7&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;priority=P1&amp;priority=P2&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Platform/Text</a>).</li>
</ul>
<h4>Undo/Redo (Markus, Tom; FAQ: Dani, Dirk)<br>
</h4>
<ul>
  <li>Test that <span style="font-weight: bold;">Refactor &gt;
Undo/Redo</span> is gone<br>
  </li>
  <li>Execute various refactorings from different views and check that <span style="font-weight: bold;">Edit &gt; Undo</span> allows undoing the
refactoring (note that not all
refactoring are undoable. So best test rename, extract method, ..)</li>
  <li>Test undo/redo of typing inside the editor (without mixing it
with refactoring undo)<br>
  </li>
  <li>Execute refactorings and change the state of affected resource
and check that the undo is no longer valid. State changes are: content
changes, bringing it out of sync with the workspace and changing
read-only state. Changing the state should not automatically flush the
undo stack anymore. Check that restoring the original state will allow
undoing the refactoring (if the file got modified and save in the Java
editor simply undo the text change. This will now restore the state).<br>
  </li>
  <li>Execute refactoring from within the Java editor and check that
the undos appear on the editor's undo stack. Test undo/redo of the
refactorings<br>
  </li>
  <li>Test mixing refactoring and typing in the editor and test
undo/redoing these.<br>
  </li>
  <li>Check that undoing a refactoring from withing the Java editor
should show a confirmation box when other resources than the file
currently being edited are affected by the undo (for example rename a
method that is referenced in a second CU and try yo undo it from the
editor that contains the declaration).</li>
  <li>Check that undoing the last change remove the dirty indication in
the editor tab<br>
  </li>
</ul>
<h4>New Open Type dialog (David, Martin; FAQ: Dirk)<br>
</h4>
<ul>
  <li>Test new open type dialog and history (know problem [<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93668">93668</a>])</li>
  <ul>
    <li>removing elements from the history using delete key or context
menu</li>
    <li>dialog doesn't show stale types in history</li>
  </ul>
</ul>
<h4>Refactoring Capture Binding (Dani, Benjamin; FAQ: Markus)<br>
</h4>
<ul>
  <li>Test refactoring and capture bindings (known problem [<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93541">93541</a>]):</li>
  <ul>
    <li>test all refactorings that deal with expressions (extract
local, constants, extract method) and create new type signature. The
expression to be extract should be of a generic type using wildcards.
For example extract foo() to a local variable where foo is declared as
follows: List&lt;?&gt; foo();</li>
  </ul>
</ul>
<h4>Build Path (Dani, Benjamin; FAQ: Martin)<br>
</h4>
<ul>
  <li>Test new access rule user interface. Access rules are defined via
the build path. Don't test it for plug-in projects since PDE takes care
of access rule here</li>
  <li>Test user interface for adding native libraries to the build path
(build path page, attribute of JARs and class folders)<br>
  </li>
</ul>
<h4>Preferences (Markus, Tom; FAQ: Martin)</h4>
<ul>
  <li>All preferences and property pages have meaningful keywords. Try
to navigate to a
preference page using a keyword that should match and validate that the
page is shown</li>
  <li>Check editor preferences. They got converted back to tab style.
Verify that nothing is clipped, tabs are visible, layout is correct</li>
</ul>
<h4>Compiler (Markus, Tom; FAQ: Martin)</h4>
<h4> </h4>
<ul>
  <li>New compiler settings for @SuppressWarnings annotation</li>
</ul>
<h4>Quick Fix/Assist<span style="font-weight: bold;"> </span>(Dani,
Benjamin; FAQ: Martin)</h4>
<ul>
  <li>Add missing @Deprecated and @Override annotation</li>
  <li>Quick fixes and wild card types: New variable with a wildcard
type, change method signature, new method....<br>
  </li>
  <li>Quick fix/assist direct shortcuts<br>
  </li>
</ul>
<h4>Add Imports (Dani, Benjamin; FAQ: Martin)<br>
</h4>
<ul>
  <li>Add import that introduces a star import removes unused fully
qualified import<br>
  </li>
</ul>
<h4>Platform-Text (David, Martin; FAQ: Tom, Dani)<br>
</h4>
<ul>
  <li>Verify syntax coloring and highlighting interaction (verify there
is no cheese due to optimizations)</li>
  <li>Use <span style="font-weight: bold;">Window &gt; New Editor</span>
on a text editor and verify that they behave property<br>
  </li>
</ul>
<h4>Java Editor (David, Martin; FAQ: Tom, Dani)</h4>
<ul>
  <li>Code assist</li>
  <ul>
    <li>auto insertion behavior</li>
    <li>parameter guessing correctness</li>
    <li>type parameter guesses (e.g. in List&lt;String&gt; l= new
ArrayList&lt;??&gt; should guess something meaningfully for ??)</li>
    <li>auto insert behavior</li>
  </ul>
  <li>auto-boxing coloring: verify that it colors the same places as
the compiler
warns about (enable corresponding compiler warning)</li>
  <li>Move lines - check performance</li>
  <li>verify that new folding artwork looks good - try with different
fonts</li>
  <ul>
    <li>icons</li>
    <li>line in vertical rule</li>
  </ul>
  <li>Use <span style="font-weight: bold;">Window &gt; New Editor</span>
on a Compilation Unit editor and verify that both behave property</li>
  <li>Use <span style="font-weight: bold;">Window &gt; New Editor</span>
on a Class File editor and verify that both behave property</li>
</ul>
<h4>Search (Dani, Benjamin; FAQ: Martin)<br>
</h4>
<ul>
  <li>Test text search</li>
  <li>Focus searching in large file with regex patterns which spawn
multiple line - larger code blocks</li>
  <li>Have an eye on performance<br>
  </li>
</ul>
<h2><a name="J2SE50"></a>J2SE 5.0</h2>
Note, when testing Java 5.0 feature don't forget to test parameterized
types that are subclasses of generic types as well as methods that use
type parameters and varargs. For example MyList extends
ArrayList&lt;String&gt; or &lt;X. void foo(X x, String...). The
examples
below are a starting point of cases to check. The list IS NOT complete.
Try to come up with your own corner cases as well. A good overview what
to test is the J2SE 5.0 status <a href="http://www.eclipse.org/jdt/ui/r3_1/j2se50/Status.html">document.</a><br>
<h4>Refactoring (David, Benjamin, Dani: coordinate the effort; FAQ: Dirk, Markus, Tobias)<br>
</h4>
<ul>
  <li>Rename<br>
  </li>
  <ul>
    <li>annotations, annotation members (especially the special case
value), enum, enum member, type parameters, vararg parameters</li>
    <li>with varargs, type parameters, generic &amp; parameterized
types in the signature (field, method, local)</li>
  </ul>
  <li>Move CU/Type</li>
  <ul>
    <li>annotations, enum, generic &amp; parameterized types<br>
    </li>
  </ul>
  <li>Move (method &amp; static members)</li>
  <ul>
    <li>enums and annotations as members in types</li>
  </ul>
  <ul>
    <li>signature with type parameters, varargs, parameterized types</li>
    <li>methods in generic &amp; parameterized types</li>
    <li>methods that refer to a static import or type parameters from
class<br>
    </li>
  </ul>
  <li>Change method signature</li>
  <ul>
    <li>signature with type parameters, varargs, parameterized types</li>
    <li>methods in annotations, enums, generic &amp; parameterized types</li>
  </ul>
  <li>Convert Anonymous to nested</li>
  <ul>
    <li>annotations, enum, generic &amp; parameterized types</li>
  </ul>
  <li>Move member type to new file</li>
  <ul>
    <li>annotations, enum, generic &amp; parameterized types</li>
    <li>code that refers to static imports</li>
    <li>code that refers to type parameters</li>
  </ul>
  <li>Pull Up &amp; PushDown</li>
  <ul>
    <li>methods in generic &amp; parameterized types</li>
    <li>methods that refer to a static import</li>
    <li>methods with type parameters, varargs, parameterized types</li>
    <li>between generic, normal and parameterized types</li>
    <li>enums and annotations as members in types</li>
  </ul>
  <li>Extract Interface / Use Supertype where possible</li>
  <ul>
    <li>enum and annotations<br>
    </li>
  </ul>
  <ul>
    <li>generic and parameterized types</li>
    <li>method with varargs, type parameters, parameterized types<br>
    </li>
  </ul>
  <li>Generalize Type</li>
  <ul>
    <li>enums and annotations</li>
    <li>generic and parameterized types</li>
  </ul>
  <li>Extract/Inline Method</li>
  <ul>
    <li>Code in generic &amp; parameterized types and enums<br>
    </li>
    <li>Code that refer to type parameters (from class and method)</li>
    <li>vararg usages</li>
    <li>code with references to static imports</li>
    <li>code with autoboxing</li>
  </ul>
  <li>Extract/Inline local</li>
  <ul>
    <li>expression which resolve to parameterized types, annotations,
enums&nbsp; and type parameters (or the concrete type for parameterized
types)</li>
  </ul>
  <li>Extract/Inline constant</li>
  <ul>
    <li>in enums, annotations, generic and parameterized types</li>
  </ul>
  <li>Introduce parameter</li>
  <ul>
    <li>expression which resolve to parameterized types, annotations,
enums&nbsp; and type parameters (or the concrete type for parameterized
types)<br>
    </li>
    <li>signature to be changed contains varargs, type parameters,
parameterized types</li>
  </ul>
  <li>Introduce Factory</li>
  <ul>
    <li>for generic and parameterized types</li>
    <li>destination type is generic or parameterized</li>
  </ul>
  <li>Convert local variable to field</li>
  <ul>
    <li>declaring type is parameterized types, annotations, enums&nbsp;
and type parameters (or the concrete type for parameterized types)</li>
  </ul>
  <li>Self encapsulate field</li>
  <ul>
    <li>field type is parameterized types, annotations, enums&nbsp; and
type parameter</li>
    <li>in enums, parameterized types and generic types.</li>
  </ul>
  <li>Infer type arguments <br>
  </li>
  <ul>
    <li>test for collection classes</li>
    <li>test for own generic classes</li>
    <li>test for classes with n type parameters<br>
    </li>
  </ul>
</ul>
<h4>Source Actions (Christof, Markus, Benjamin; FAQ: Tobias)<br>
</h4>
<div style="margin-left: 40px;">Don't forget to check the Javadoc for
the generated methods<br>
</div>
<ul>
  <li>Organize import / add import</li>
  <ul>
    <li>organize import. Define static import groups in the preference</li>
    <li>add import on Math.max should add a static import on max add
should remove Math in code.</li>
  </ul>
  <li>Override/Implement methods</li>
  <ul>
    <li>methods with type parameters, varargs, parameterized types</li>
    <li>from generic and parameterized types</li>
    <li>from annotations</li>
  </ul>
  <li>Generate Getter/Setter</li>
  <ul>
    <li>field type is parameterized types, annotations, enums&nbsp;
and type parameters</li>
    <li>in enums, parameterized types and generic types</li>
  </ul>
  <li>Generate Delegate Methods</li>
  <ul>
    <li>field type is enum, annotation</li>
    <li>field type is type parameter or parametrized type</li>
  </ul>
  <li>Generate Constructor Using fields</li>
  <ul>
    <li>field type is enum, annotation</li>
    <li>field type is type parameter or parametrized type</li>
  </ul>
  <li>Add Constructor from Superclass</li>
  <ul>
    <li>super class is generic or parameterized type</li>
    <li>constructor with type parameters, varargs, parameterized types</li>
  </ul>
  <li>Sort members</li>
  <ul>
    <li>members with type parameters, varargs, ...</li>
    <li>types with enums, annotations, generic and parameterized types
as members<br>
    </li>
    <li>sort enum, annotations, generic and parameterized types<br>
    </li>
  </ul>
</ul>
<h4>Search (Dani, Benjamin; FAQ: Markus, Martin, Dirk)</h4>
<ul>
  <li>test searching for enums, annotations, generic types and methods,
parameterized types and methods and type variables</li>
  <li>test new filters for incompatible and inexact matches</li>
</ul>
<h4>Quick Fix &amp; Quick assist (Tom, Markus; FAQ: Martin)<br>
</h4>
<ul>
  <ul>
  </ul>
  <li>Test convert to enhanced for loop (currently only available for
arrays)<br>
  </li>
  <li>Javadoc tags for type parameters (handled special. creates
&lt;T&gt;)</li>
  <li> quick fix helps you changing the compliance settings when you
try
to enter 5.0 constructs in a 1.4 project. Note that a 1.5 JRE is
required which has to be added in the 'Installed JRE's' preference page</li>
</ul>
<h4>Java Editor (Tobias, Martin; FAQ: Tom)<br>
</h4>
<ul>
  <li>new syntax colorings</li>
  <ul>
    <li>auto(un)boxed expressions</li>
    <li>new keywords (enum, @interface)<br>
    </li>
    <li>annotations</li>
    <li>annotation element references</li>
    <li>parameter variables<br>
    </li>
  </ul>

  <li>code assist</li>
  <ul>
    <li>enums</li>
    <li>static imports<br>
    </li>
    <li>generics
			</li>
  </ul>
  <ul>
    <li>type parameter proposals</li>
  </ul>
  <ul>
    <li>enum constant proposals</li>
    <li>annotations<br>
    </li>
  </ul>
  <ul>
    <li>argument guessing for parameterized types</li>
  </ul>
  <li>verify that the Java Outline displays new J2SE 5.0 constructs correctly</li>
  <li>verify that occurrence marking handles new J2SE 5.0 elements
correctly (check bugzilla first: there are already some bug reports)</li>
  <li>verify that folding works correctly for J2SE 5.0 elements</li>
  <li>test new 'foreach' template</li>
  <li>hovers for new J2SE 5.0 constructs (e.g. hovering over parametrized types)</li>
  <li>format CUs with J2SE 5.0 constructs and verify that they get correctly formatted according to the current formatter settings<br>
  </li>

  
</ul>

<h2>New 3.1 Functionality (in addition to <a href="../../../../../../new%20and%20noteworthy/whats-new-template.html">J2SE 5.0</a>)<br>
</h2>
<h4>Preferences (Tobias; FAQ: Martin)<br>
</h4>
<ul>
  <li>test that you can navigate from project specific settings to the
global settings and vice versa</li>
  <li>test project specific settings for formatter, compiler, code
style settings, Javadoc locations</li>
  <li>test the new hyperlinks on Text Editor and Java preference pages: verify that</li>
  <ul>
<li>link is correctly shown</li>
    <li>hover is correct<br>
    </li>
<li>clicking navigates to correct preference page<br>
</li>
  </ul>

</ul>
<h4>Search (Dani, Christof; FAQ: Dirk)<br>
</h4>
<ul>
  <li>Test different rendering of filtered / non filtered search result
matches</li>
  <li>occurrence search</li>
  <ul>
    <li>Implementing Methods<br>
    </li>
  </ul>
  <ul>
    <li>Throwing Exception</li>
  </ul>

</ul>
<h4>Quick fixes (Benjamin, Dani FAQ: Martin) <br>
</h4>
<ul>
  <li>Serial version Id<br>
  </li>
</ul>
<h4>Text Editor (Tobias, Martin; FAQ: Dani, Tom)<br>
</h4>
<ul>
  <li>URL hyperlinking: verify that</li>
  <ul>
    <li>link is correctly indicated</li>
    <li>clicking shows the URL in a browser</li>
  </ul>
  <li>test new encoding support</li>
  <li>open Properties dialog from active editor</li>
  <li>test 'Convert Line Delimiter To' commands on active editor and on a folder or project</li>
  <li>test 'Remove Trailing Whitespace' command on active editor and on a folder or project</li>
  <li>test 'Word Completion' (Ctrl + /)</li>
  <li>verify that the new undo history size preference correctly works<br>
  </li>

  
</ul>
<h4>Java Editor (Martin, Dirk; FAQ: Dani, Tom)<br>
</h4>
<ul>
  <li>semantic coloring for deprecated members</li>
  <li>verify the new underline and strikethrough syntax coloring styles</li>
  <li>new occurrence markings</li>
  <ul>
    <li>inherited methods</li>
    <li>implements occurrences</li>

  </ul>
  <li>folding</li>
  <ul>
    <li>header folding: test different variants of headers<br>
    </li>
  </ul>
  <ul>
    <li>better caption when Javadoc or code is folded</li>
  </ul>
  <li>test that the browser widget is used for Javadoc information presentation (F2)</li>
  <ul>
    <li>verify that performance is acceptable<br>
    </li>
  </ul>

  
</ul>
<h4>NLS Tooling (Dirk, David; FAQ: Dani)<br>
</h4>

<ul>
  <li>test Externalize Strings wizard with new Eclipse-style message
bundles</li>
  <li>test Externalize Strings wizard with old-style message
bundles</li>

  <li>linking in CU and Class File editor to properties entry
and vice versa (only works for old-style NLSing)</li>
  <li>hovering over NLS key in CU and Class File editor show externalized string (only works for old-style NLSing)</li>
  <li>Java Properties File editor</li>
  <ul>
    <li>syntax coloring - verify that colors can be changed via preferences</li>
    <li>spell checking<br>
    </li>
  </ul>
</ul>
<ul>

</ul>

<h4>New Source Folder wizard page (David; FAQ: Martin)<br>
</h4>
<ul>
  <li>setup project on existing source using the new source folder
wizard page.</li>
  <li>Source to setup should have:</li>
  <ul>
    <li>multiple source folders</li>
    <li>need to exclude some portion of the code<br>
    </li>
  </ul>
</ul>
<h2>General items<br>
</h2>
<h4>Accessibility Testing (Tom)<br>
</h4>
<ul>
  <li>verify mnemonics in wizards/dialogs/menus<br>
    <i>Note: mnemonics on Platform Text and JDT Text preference pages
are not yet done.</i></li>
  <li>initial focus in dialogs</li>
  <li>combination of color, form, and text. </li>
  <li>status line information</li>
</ul>
<h4>Operations and Locked Workspace (Dirk, Christof)</h4>
<ul>
  <li>To lock the workspace use the org.eclipse.ui.examples.job plug-in
from the Eclipse repository</li>
  <li>Test Edit, Source and Refactoring actions when the workspace is
locked</li>
  <li>Test modifying project properties (build path, compiler settings,
...) when workspace is locked</li>
  <li>You should always get the blocking dialog</li>
  <li>Cancel the user action. Make sure that no
OperationCancelException or other exceptions appear in the log</li>
</ul>
<h4>Validate-Edit (Tobias; FAQ: Dani)</h4>
<ul>
  <li>Check-out code from the repository in CVS Watch/Edit mode (stores
file in read-only mode)</li>
  <li>Test Editing, Source and Refactoring actions on files that are
read-only</li>
  <li>Expected result: actions should complete without errors</li>
</ul>
<h4>Compilation Units not on Build Path (Dirk, Christof; FAQ: Dani, Dirk)&nbsp;</h4>
<ul>
  <li>Test Edit, Source and Refactoring actions for compilation units
not on the build path.</li>
  <li>Test for:
    <ul>
      <li>editors opened on repository files</li>
      <li>editors opened on Java file excluded from the build path</li>
      <li>editors opened on Java files stored in Simple projects </li>
    </ul>
  </li>
  <li>Actions should either operate without an error, not be present or
present a dialog that the CU is not on the build path</li>
</ul>
<h4><font color="#000000">Workspace compatibility (Markus)</font></h4>Verify
that an existing workspace can be started on the new version and is
fully functional. Check the .log for serious problems.<br>

<ul>
  <li>upgrade a 3.0 workspace to 3.1</li>
  <li>upgrade a 2.1 workspace to 3.1<br>
  </li>

</ul>
</body></html>